Safety and Liveness for an RBAC/MAC Security Model

Our role-based/mandatory access control (RBAC/MAC) security model and enforcement framework for inter-operating legacy, COTS, GOTS, databases, servers, etc., limits: who (user/user role) can invoke which methods (based on value and MAC level) of artifact APIs at what times, and who (user) can delegate which responsibility (user role) at what times. In this chapter, we focus on assurance for the timeframe of access (of a user to a role, of a role to a method, etc.) and the attainment of the Simple Security Property (i.e., a subject cannot read information for which it is not cleared) and Simple Integrity Property (i.e., a subject is limited to writing information at its own level and lower), which together can be used to support safety and liveness.